When I create a change proposal partner for a module, the system uses the first 150 objects and fills the heading text with numbers. I need to have most of these objects available for use. Is there a way to set the number of objects created to a value, such as 1 or 10? What drives the number of objects that are populated? I have tried creation with and without selection of attributes for configure.
lahines - Wed Apr 13 10:01:54 EDT 2011 |
|
Re: Change proposal partner creation llandale - Wed Apr 13 15:23:21 EDT 2011
The Change Proposal module has a heading structure that corresponds to all the valid folks configured for CPS in that project. The number you see is the User's "Unique ID" in 16 digit octal format; of course that means that its mostly prefixed with zeros.
When you add a new person to the CPS, the sibling "Users" module and ALL the CPS modules are updated with a new heading for that user; which may take a long time.
The purpose of these headings is to allow both you and someone else to submit proposals to the same module at the same time. When you submit, YOUR section in the CPS module is locked and the CP is created therein.
It scares me a little that you are even LOOKING in that module. CPS provides sloppy mechanics for reviewing your CPs, you should not need to look in the partner module. And you must definately NEVER modify anything therein directly or you will invalidate your service agreement ... or so they say.
|
|
Re: Change proposal partner creation lahines - Wed Apr 13 15:52:39 EDT 2011 llandale - Wed Apr 13 15:23:21 EDT 2011
The Change Proposal module has a heading structure that corresponds to all the valid folks configured for CPS in that project. The number you see is the User's "Unique ID" in 16 digit octal format; of course that means that its mostly prefixed with zeros.
When you add a new person to the CPS, the sibling "Users" module and ALL the CPS modules are updated with a new heading for that user; which may take a long time.
The purpose of these headings is to allow both you and someone else to submit proposals to the same module at the same time. When you submit, YOUR section in the CPS module is locked and the CP is created therein.
It scares me a little that you are even LOOKING in that module. CPS provides sloppy mechanics for reviewing your CPs, you should not need to look in the partner module. And you must definately NEVER modify anything therein directly or you will invalidate your service agreement ... or so they say.
DOORS does not provide the option of splitting the change partner when splitting a module into two modules, both of which need changes applied. The change approval documentation is based on the absolute number of the change partner. The change partner isn't black magic and your explanation helps explain the number of sections that initally appear in the change module. Since I cannot go back in time and reduce the number of users, I probably cannot reproduce the change module but will have to work out some sort of conversion table.
|
|
Re: Change proposal partner creation llandale - Wed Apr 13 16:23:59 EDT 2011 lahines - Wed Apr 13 15:52:39 EDT 2011
DOORS does not provide the option of splitting the change partner when splitting a module into two modules, both of which need changes applied. The change approval documentation is based on the absolute number of the change partner. The change partner isn't black magic and your explanation helps explain the number of sections that initally appear in the change module. Since I cannot go back in time and reduce the number of users, I probably cannot reproduce the change module but will have to work out some sort of conversion table.
So you have configured a module for CPS, created a bunch of proposals, and now want to split the original source module into two modules yet preserve the CPs for all objects.
Yes, CPS doesn't support that. You will need to split up your module, configure CPS for the new module, and recreate all of the proposals for objects in the new module.
Having said that, and re-affirming that you should not monkey with CPS ... if it were me working theoretically on some test database and would never never never never never do this on a production database for fear of losing Support ... I would, again purely theoretically, do this:
Copy the source module. Delete all its newly created out link sets which will remove all its outlinks.
Copy the partner CPS module. Delete all its newly created out link sets (which, BTW, will go to the original Source).
Open the Change Proposal System link module and create a linkset from the new CPS module to the new copy of Source.
Define a default link module from new CPS to new Source using the Change Proposal Links module.
Strip down the original source module, deleting objects intended for the copy.
Strip down the copy, deleting objects intended to be preserved in the source.
Strip down the new CPS module, deleting CPs that apply to the original.
Strip down the old CPS module, deleting CPs that are associated with Copy Source.
For each remaining new CP, link it manually to the corresponding new Source object. This is achievable since the "Object Text" of the CP contains the Identifier of the intended target object. Actually, I'd write a script to do this.
Deal with CP groups somehow; haven't given that a lot of thought.
Again, purely theoretically, I would not tell IBM I did ..err.. theoretically did that.
Of course I'd practice on a test database first. Not theoretically, actually.
|
|
Re: Change proposal partner creation SystemAdmin - Wed Apr 13 18:06:17 EDT 2011 lahines - Wed Apr 13 15:52:39 EDT 2011
DOORS does not provide the option of splitting the change partner when splitting a module into two modules, both of which need changes applied. The change approval documentation is based on the absolute number of the change partner. The change partner isn't black magic and your explanation helps explain the number of sections that initally appear in the change module. Since I cannot go back in time and reduce the number of users, I probably cannot reproduce the change module but will have to work out some sort of conversion table.
The DOORS CPS is a lightweight Change Management System - it's just an add-on tool that was never designed to be a sophisticated and malleable Change Management tool in the same league as the IBM Rational ClearQuest and IBM Rational ChangeSynergy applications - perhaps one of the these two or some other purpose built Change Man tool should be considered - but don't get sucked into believing that an electronic integration with DOORS is essential though - humanware integration often beats any perceived advantage of these software integrations.
The DOORS CPS can be really useful in DOORS projects where the level of requirements management (RM) sophistication is also lightweight, that is, there's a degree of predictability about the RM life-cycle for the life of the project and change management is totally confined to users of DOORS (Project team members who don't actively use DOORS will not like the DOORS CPS).
Paul Miller
Melbourne, Australia
|
|
Re: Change proposal partner creation lahines - Thu Apr 14 07:08:03 EDT 2011 llandale - Wed Apr 13 16:23:59 EDT 2011
So you have configured a module for CPS, created a bunch of proposals, and now want to split the original source module into two modules yet preserve the CPs for all objects.
Yes, CPS doesn't support that. You will need to split up your module, configure CPS for the new module, and recreate all of the proposals for objects in the new module.
Having said that, and re-affirming that you should not monkey with CPS ... if it were me working theoretically on some test database and would never never never never never do this on a production database for fear of losing Support ... I would, again purely theoretically, do this:
Copy the source module. Delete all its newly created out link sets which will remove all its outlinks.
Copy the partner CPS module. Delete all its newly created out link sets (which, BTW, will go to the original Source).
Open the Change Proposal System link module and create a linkset from the new CPS module to the new copy of Source.
Define a default link module from new CPS to new Source using the Change Proposal Links module.
Strip down the original source module, deleting objects intended for the copy.
Strip down the copy, deleting objects intended to be preserved in the source.
Strip down the new CPS module, deleting CPs that apply to the original.
Strip down the old CPS module, deleting CPs that are associated with Copy Source.
For each remaining new CP, link it manually to the corresponding new Source object. This is achievable since the "Object Text" of the CP contains the Identifier of the intended target object. Actually, I'd write a script to do this.
Deal with CP groups somehow; haven't given that a lot of thought.
Again, purely theoretically, I would not tell IBM I did ..err.. theoretically did that.
Of course I'd practice on a test database first. Not theoretically, actually.
You know, that is a good idea. The link wizard might easily accomplish this task.
|
|
Re: Change proposal partner creation lahines - Thu Apr 14 07:10:23 EDT 2011 lahines - Thu Apr 14 07:08:03 EDT 2011
You know, that is a good idea. The link wizard might easily accomplish this task.
Then again, it might be slightly more complicated. Thanks for your input.
|
|
Re: Change proposal partner creation llandale - Thu Apr 14 18:04:14 EDT 2011 SystemAdmin - Wed Apr 13 18:06:17 EDT 2011
The DOORS CPS is a lightweight Change Management System - it's just an add-on tool that was never designed to be a sophisticated and malleable Change Management tool in the same league as the IBM Rational ClearQuest and IBM Rational ChangeSynergy applications - perhaps one of the these two or some other purpose built Change Man tool should be considered - but don't get sucked into believing that an electronic integration with DOORS is essential though - humanware integration often beats any perceived advantage of these software integrations.
The DOORS CPS can be really useful in DOORS projects where the level of requirements management (RM) sophistication is also lightweight, that is, there's a degree of predictability about the RM life-cycle for the life of the project and change management is totally confined to users of DOORS (Project team members who don't actively use DOORS will not like the DOORS CPS).
Paul Miller
Melbourne, Australia
... actually, project team folks who don't use DOORS just LOVE CPS, since they don't have to deal with it, let someone else do the work.
|
|